Compare Page

Data maintenance

Characteristic Name: Data maintenance
Dimension: Availability and Accessability
Description: Data should be accessible to perform necessary updates and maintenance operations in it’s entirely
Granularity: Record
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to lack of data maintenance
The number of complaints received due to lack of continuity in data access

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Technological changes in the infrastructure/system should be handled in such a way that they should not make data inaccessible (1) Sales order is created once a customer signs a contract. Then it is updated in three instances 1)Delivery date and shipment date is updated once the production plan is created. 2) Actual quantity is updated once the manufacturing is complete 3) Total cost is updated once the freight changes are incurred. A sales order is achieved after one years from delivery.
A maintenance policy for mission critical data should be developed and implemented to handle on going systematic updates (Create, read, update, delete, archive and cleanse) (1) Customer data : Created when a customer enters into a contract, updated once the customer details change or contact change, archived once the contact end
When multiple versions of the same data is available through different datasets\databases create a master record and make it available across the systems (1) Master data management
Leverage application and storage technology in such a way that the maintenance policies can be applied on data (1)Addresses which were not updated during the last 24 months are prompted for validations
Create a responsibility structure/Authorisation structure and a communication structure to manage the process of information generation maintenance and utilisation (1) It is the responsibility of the work study team to provide SMV (standard minute values) for a garment.
(2) Approved SMVs should be sent to the planning department for planning purposes.

Validation Metric:

How mature is the data maintenance process

These are examples of how the characteristic might occur in a database.

Example: Source:
minutes of a meeting will be produced in draft form and reviewed by the members of the committee before being approved. Once this process of creation is finished the record must be fixed and must not be susceptible to change. If a record is changed or manipulated in some way, it no longer provides evidence of the transaction it originally documented. For example, if someone alters the minutes of a meeting after they have been approved, the minutes can no longer be considered an accurate record of the meeting. This is another issue that becomes more important in an electronic context. K. Smith, “Public Sector Records Management: A Practical Guide”, Ashgate, 2007.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
A measure of the degree to which data can be accessed and used and the degree to which data can be updated, maintained, and managed. D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
Can all of the information be organized and updated on an on-going basis? EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer.

 

Data volume

Characteristic Name: Data volume
Dimension: Completeness
Description: The volume of data is neither deficient nor overwhelming to perform an intended task
Granularity: Information object
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to not meeting the right volume of data
The number of complaints received due to volume related issues

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Define the scope of data in terms of organisational coverage to perform a business activity (1) At least 70% of the production units should submit data to calculate total production efficiency of the company
Define the scope of data in terms of activities relates to any business task (1) Pages with more than thousand
hits per day and above are considered for the analysis
Define the scope of data in terms of the population of data which is under concern (1) At least 10% of the population of white blood cells in the culture should be collected as samples to calculate its growth
Define an appropriate amount of records in terms of lower limit and upper limit for any task (1) At least six responses should be available to evaluate a tutor's skills and competency.

Validation Metric:

How mature is the process of defining and maintaining appropriate data volumes of data

These are examples of how the characteristic might occur in a database.

Example: Source:
At the end of the first week of the Autumn term, data analysis was performed on the ‘First Emergency Contact Telephone Number’ data item in the Contact table. There are 300 students in the school and 294 out of a potential 300 records were populated, therefore 294/300 x 100 = 98% completeness has been achieved for this data item in the Contact table. N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
A measure of the availability and comprehensiveness of data compared to the total data universe or population of interest. D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
Is the scope of information adequate? (not too much nor too little). EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer.
Degree of presence of data in a given collection. SCANNAPIECO, M. & CATARCI, T. 2002. Data quality under a computer science perspective. Archivi & Computer, 2, 1-15.
The quantity or volume of available data is appropriate WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.